chore(deps): update dependency wrangler to ^4.90.0#9
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update dependency wrangler to ^4.90.0#9renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
floren | f294b69 | Commit Preview URL Branch Preview URL |
May 08 2026, 08:18 AM |
1588f50 to
553b182
Compare
553b182 to
c81ed38
Compare
1424882 to
bf51f80
Compare
bf51f80 to
45962c8
Compare
45962c8 to
f294b69
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.87.0→^4.90.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.90.0Compare Source
Minor Changes
#12279
248bc08Thanks @penalosa! - Add deprecation warning fordelivery_delayin queue producer bindingsThe
delivery_delaysetting in[[queues.producers]]was silently having no effect since 2024. This change adds a deprecation warning when the setting is used, informing users that queue-level settings should be configured usingwrangler queues updateinstead. The setting will be removed in a future version.Patch Changes
#13853
8852b0cThanks @gpanders! - Fix Containers SSH config#13858
e414e56Thanks @penalosa! - Fixwrangler whoamiand account selection failing for Account API TokensThe
/membershipsfallback for Account API Tokens was checking for code 9109, but/membershipsactually returns 9106 for that case. Correct the code so the fallback to/accountstriggers as intended.Updated dependencies []:
v4.89.1Compare Source
Patch Changes
#13824
dd3baf3Thanks @emily-shen! - Fix container deployment being skipped for Workers for Platforms user workersPreviously, deploying a worker with
--dispatch-namespacewould early-exit before callingdeployContainers(), meaning container-app registration that links the image to the Durable Object namespace was never executed for WfP user workers. Container deployment now runs before the WfP early exit.Updated dependencies [
5cf6f81]:v4.89.0Compare Source
Minor Changes
#13055
f3fed88Thanks @GregBrimble! - Introducing thecacheconfiguration option for Workers.You can now set
{ cache: { enabled: true } }in your Wrangler configuration file to enable a HTTP cache in front of your Worker'sfetchhandler. This is also supported in[previews]configuration —previews.cacheoverrides the top-levelcachesetting for preview deployments, and falls back to the top-level value when absent. More information can be found in our documentation.#13776
1a54ac5Thanks @petebacondarwin! -wrangler devand other Miniflare-backed commands now run the localworkerdruntime withTZ=UTCto match productionPreviously,
wrangler dev(and other commands that spin up Miniflare, such aswrangler kv,wrangler d1,wrangler r2,wrangler check) inherited the host machine's timezone, soDateandIntlAPIs inside a Worker observed the developer's local timezone during local development but UTC in production. This caused subtle, hard-to-debug differences between local and deployed behaviour.Local development now matches production. Code that previously relied on the host timezone during
wrangler devwill need to either accept UTC (the production behaviour) or explicitly construct dates/formatters with the desired timezone.Patch Changes
#13829
2284f20Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#13841
332f527Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#13777
18e833dThanks @matingathani! - fix: throw a clear error when _routes.json contains invalid JSON instead of silently skipping it#13751
b6cea17Thanks @matingathani! - fix: ensurewrangler types --check --env-filedoes not falsely report stale types when.dev.varsexists#13775
53e846aThanks @maxwellpeterson! - Fixwrangler previewnot propagating theassetsbinding to preview deploymentsPreviously,
wrangler previewwould upload the asset manifest correctly but the resulting preview deployment had noASSETSbinding (or whatever name was configured underassets.binding). Workers reading from the binding would seeundefinedand fail at runtime.The fix emits the assets binding into the deployment's
envmap alongside other bindings, mirroringwrangler deploy.#13770
beff19cThanks @petebacondarwin! - Only show accounts available for the current login auth inwrangler whoamiand the interactive account pickerWrangler now lists the intersection of
/accountsand/membershipsinstead of either endpoint alone, dropping accounts the active OAuth token or API token has no membership in. Theaccountsfield ofwrangler whoami --jsonis filtered the same way. When/membershipsis inaccessible to the current auth (e.g. Account API Tokens) Wrangler falls back to/accountsso those tokens continue to work as before.#13832
af42fedThanks @gpanders! - Showcontainers sshinwrangler containers --helpand inwrangler containers ssh --helpThe
containers sshcommand was previously hidden, so it did not appear in the list of subcommands shown bywrangler containers --help, and its description was omitted fromwrangler containers ssh --help. The command is now listed with its description in both places.Updated dependencies [
2284f20,332f527,039bada,1a54ac5]:v4.88.0Compare Source
Minor Changes
#13760
e07825aThanks @danielgek! - Addbuiltinstorage option towrangler ai-search create.wrangler ai-search createnow supports a third storage type,builtin, in addition tor2andweb-crawler. When--type builtinis selected (or chosen interactively), Wrangler creates the instance using Cloudflare-managed storage by omittingtypeandsourcefrom the API request — the API treats an absenttypeas builtin storage. Builtin instances do not accept--source,--prefix,--include-items, or--exclude-items.#13721
58899d8Thanks @danielgek! - Add optionalcustom_metadatastep towrangler ai-search createThe
wrangler ai-search createinteractive wizard now lets you declare custom metadata fields that the new AI Search instance should index. Each field is afield_namepaired with adata_type(text,number,boolean, ordatetime).You can provide fields up-front via the new repeatable
--custom-metadataflag usingfield_name:data_typesyntax:For larger schemas, use
--custom-metadata-schemato point at a JSON file containing an array of{ field_name, data_type }objects:[ { "field_name": "title", "data_type": "text" }, { "field_name": "views", "data_type": "number" } ]#13701
18b9d5bThanks @dario-piotrowicz! - Prompt for missing name and compatibility date interactively duringwrangler deployWhen deploying without a project name or
compatibility_datein your configuration or CLI arguments,wrangler deploynow interactively prompts for the missing values instead of immediately failing with an error. For compatibility date, the prompt offers to use today's date; if you decline, the existing error is shown. The compatibility date prompt is skipped when--latestis passed. In non-interactive or CI environments, behavior is unchanged.Additionally, when no config file exists,
wrangler deploynow offers to save the prompted name and compatibility date to awrangler.jsoncfile for future use. This interactive flow is available for allwrangler deployinvocations — not just asset-only deployments.#13810
2b8c0ccThanks @jamesopstad! - Stabilize thesecretsconfiguration propertyThe
secretsproperty in the Wrangler config file is no longer experimental and will no longer emit an experimental warning when used. Required secrets are validated during local development and deploy, and used as the source of truth for type generation.{ "secrets": { "required": ["API_KEY", "DB_PASSWORD"] } }Patch Changes
#13765
3020214Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#13800
0099265Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#13812
25f5ef2Thanks @emily-shen! - fix:--aliasCLI flag now works inwrangler deployThe
--aliasflag was accepted but silently ignored duringwrangler deploy— onlyconfig.aliastook effect. We now collect aliases from both config and CLI flags.#13772
194d75eThanks @zakcutner! - Fixwrangler typesto generateFetcherforunsafe.bindingsentries withtype: "service"Previously, all entries in
unsafe.bindings(other thanratelimit) generated a fallbackanytype.wrangler typesnow generatesFetcherfor unsafe bindings declared withtype: "service", matching the type used for regular service bindings.#13818
9f532f7Thanks @1000hz! - Support Flagship bindings in Worker Previewswrangler previewnow acceptsflagshipentries in thepreviewsblock and includes them in Preview deployment bindings. This lets Workers that use Flagship bindings deploy Preview versions with preview-specific Flagship app IDs.#12974
1127114Thanks @ask-bonk! - Fixpropsand fetcher-type service bindings being dropped inunstable_getMiniflareWorkerOptionsThe post-processing in
unstable_getMiniflareWorkerOptionswas rebuildingserviceBindingsfrom scratch, which silently droppedpropson service bindings and droppedfetcher-type bindings entirely. It was also re-derivingdurableObjectsidentically to whatbuildMiniflareBindingOptionsalready produces. Both have been removed;buildMiniflareBindingOptionsnow produces the final bindings unchanged.#13739
3ceadefThanks @edmundhung! - Skip confirmation prompts inwrangler versions deploywhen versions are provided as CLI argumentsPassing version IDs or version specs to
wrangler versions deploynow applies those values directly instead of opening interactive prompts to confirm the same versions and percentages. This makes the command easier to automate without requiring--yes.#13745
1a5cc86Thanks @edmundhung! - fix: preserve request ports inOriginandRefererheaders when usingwrangler dev --hostUpdated dependencies [
3020214,0099265,bb27219,12fb5db]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.